home *** CD-ROM | disk | FTP | other *** search
-
- AMAX Version 1.01
- Description of Changes From Previous Version
-
- Copyright (C) 1988 Alan D. Applegate, All Rights Reserved
-
-
-
- Command Line Changes
-
- To allow for current and future expansion of command line options, the command
- line parameters and style have changed.
-
- To specify a configuration on the command line, YOU MUST NOW USE A NEW FORMAT,
- specifying the -c option. For example, to use a configuration file called
- MYFILE.CFG in the OPUS subdirectory on C: drive, use this format:
-
- amax -cc:\opus\myfile.cfg
-
- Partial Solution for X00 FOSSIL Problems
-
- Reports continue to come in that AMAX will sometimes flatly refuse to find a
- FOSSIL driver (even if one exists) when the X00 driver is used. I have no idea
- why this is. I follow the written FOSSIL specifications, and adhere to
- established standards for detecting the presence of a FOSSIL driver. Why AMAX
- can't find X00 is a mystery to me.
-
- Two solutions exist.
-
- First, switch to Opus!Comm 5.xx for your FOSSIL needs. I wrote AMAX with this
- FOSSIL installed on my system, and have never once had a FOSSIL related problem
- with it.
-
- Second, continue to use X00, and use the new -n command line option. This tells
- AMAX NOT TO INITIALIZE THE FOSSIL. NOTE: USE THIS AT YOUR OWN RISK! If you
- use the -n option without a FOSSIL installed, I'm not sure what will happen,
- outside of locking-up your machine.
-
- With -n in use, AMAX will start using the FOSSIL services without verifying that
- they are even available. Hopefully this will solve some problems with systems
- that use X00, but it is risky.
-
- Sample command lines:
-
- amax -cc:\binkley\binkley.cfg -n
-
- amax -n
-
-
-